|
|
Hi Kinbay Please update me by 11:00 AM (KT) Thank you YK.Jung |
|
|
Hi YK We have no experience with this new feature So we can't estimate this new feature schedule. Perhaps you can ask Amlogic to estimate the function. BR, Kinbay |
|
|
Hi Younkwang This is the sop to update STB deviceid, widevinekey and attestaionkey. All commands need to be executed under root permission and ATV10. keylist_SKB168 and BFX-AT100_2019_002400001.keybox will be provided after business discussion. Best Regards. Liuling Wang ReadMe.txt (1,497 bytes) |
|
|
Hi LiuLing Thank you for update I'll update you after I get and test the key file Thank you YK.Jung |
|
|
Hi Younkwang Keylist and keybox are ONLY for "BFX-AT100_2019_002497681-BFX-AT100_2019_002497682" 2 units use. Please try to update these information by sop, thank you. Best Regards. Liuling Wang keylist_SK168-2units.txt (1,834 bytes) |
|
|
Hi LiuLing We have no experience with Key And I am going to test for two UHD4 STBs. Please describe it in detail with the command in the mantis below. https://btracker-cns.fii-foxconn.com/vaas/view.php?id=2028#c17314 Thank you YK.Jung |
|
|
Hi LiuLing I am testing with test key 1) In keylist_SK168-2units.txt, is the location of the wv key fixed? I would like to know about the rules for extracting the wv key at keylist_SK168-2units.txt or does the wv key always start with "4246582.." ? 2) What starts with 30303030.. in the middle? Is it an HDCP key? 3) "writeAttentionkey" executable does not exist Please share the information about the file. Thank you YK.Jung image.png (15,573 bytes) |
|
|
Hi Younkwang >>1) In keylist_SK168-2units.txt, is the location of the wv key fixed? I would like to know about the rules for extracting the wv key at keylist_SK168-2units.txt or does the wv key always start with "4246582.." ? Yes,the location of the wv key is fixed, the fourth column. The wv key is generated by Google, we do not know the rules. >>2) What starts with 30303030.. in the middle? Is it an HDCP key? Yes,but they are analog data in keylist_SK168-2units.txt, we don't need to update HDCP key this time. >> 3) "writeAttentionkey" executable does not exist Please share the information about the file. I am sorry that I forgot to upload writeAttentionkey file. Best Regards. Liuling Wang writeAttestaionkey (16,120 bytes) |
|
|
Hi LiuLing Fail is occurring in the operation below. ================================================================================= 127|BFX-AT100: # /data/writeAttestaionkey /data/BFX-AT100_2019_002400001.keybox /data/writeAttestaionkey[1]: syntax error: unexpected '}' 1|BFX-AT100: # ================================================================================= please check it, Thank you YK.Jung image-2.png (9,790 bytes) |
|
|
Hi Younkwang Please try again, thank you. Best Regards. Liuling Wang |
|
|
Hi LiuLing 1) The result of writeAttentionkey seems to be OK. But how do I verify that it's written correctly? , ( image.png ) 2) The result of widevinekey is OK ( image.png) I compare the output of echo "$var" with echo SRC WV_KEY Thank you YK.Jung image-3.png (13,046 bytes) image-4.png (34,148 bytes) |
|
|
Hi Younkwang To verify attentionkey, you can operate these commands as below: ============================================================ // Attestaionkey sha256 from file shavar=`sha256sum /data/BFX-AT100_2019_002400001.keybox | awk '{printf $1}'` echo "$shavar" // Attestaionkey dump from unifykey echo attestationkeybox > /sys/class/unifykeys/name var=`busybox hexdump -e '16/1 "%02x"' /sys/class/unifykeys/read` echo "$var" ============================================================ Compare the output of echo "$var" with echo "$shavar".If they are the same, it indicates that the attestaionkey has been set successfully Best Regards. Liuling Wang |
|
|
Hi LiuLing Thank you for update I'll test more various cases , let you know if there's anything questions Thank you YK.Jung |
|
|
Hi LiuLing I wrote a another wv_key in the presence of a widevine key, but the var is not being updated. ======================================================================== echo widevinekeybox > /sys/class/unifykeys/name echo $wv_key1 | xxd -p -r > /sys/class/unifykeys/write var=`busybox hexdump -e '16/1 "%02x"' /sys/class/unifykeys/read` echo "$var" <-- not update ======================================================================== The previous test was without a wv key I think we need to do clear or erase in the state when there is a wv key at STB Please check it Thank you YK.Jung |
|
|
Hi LiuLing I tested it again and it's being written normally. Please ignore my request (#c17331) Thank you YK.Jung |
|
|
Hi LiuLing To make sure You only gave me one attestationkey. (BFX-AT100_2019_002400001.keybox) Can I use this one key for all boxes? That is For widevine keys, one is assigned per STB, and we can use the attestationkey in common. Is it correct? Thank you YK.Jung |
|
|
Hi Younkwang >>That is For widevine keys, one is assigned per STB, and we can use the attentionkey in common. Is it correct? I am sorry, We need to discuss internally before replying. Best Regards. Liuling Wang |
|
|
Hi liuling Please ignore this contents. Thank you |
|
|
Hi Younkwang >> That is For widevine keys, one is assigned per STB, and we can use the attentionkey in common. Is it correct? (#0017339) After ALT confirms the required quantity, Fii will apply both the Attention key and WideVine key. For the WideVine key, it's assigned per STB. For the Attention key, it follows Google rule to assign the corresponding quantity. Best Regards. Liuling Wang |
|
|
Hi Younkwang For comment #0017341 The user-side fw must be approved by Google. Best Regards. Liuling Wang |
|
|
Hi Liu-Ling Wang, During the test, Chromecast did not work, so I checked and found that Chromecast does not work in the following cases. 1. Write widevine key with UHD4 (OS 10) 2. Check the chromecast is working after upgrade to Smart3 2-1. Update Smart3 (OS10) -> Chromecast is working well 2-2. Update Smart3 (OS12) -> Chromecast is not working. On the Phone, "Untrusted device" message is showing. I already checked that the SHA256 value of widevine is same between Smart3 OS10 and Smart3 OS12. Could you please check the there is anything I missed? Thank you. Kim |
|
|
Hi Kim The "Untrusted device" error on Android 12 with Chromecast,specifically affecting second-generation Chromecast and Chromecast Audio devices,is caused by an expired certificate.Google has acknowledged the issue and is rolling out a fix,which involves an update to the Google Home app.If you've already factory reset your device,you may need to set your phone's date back before March 9,2025,and then set it up again. Explanation: 1)Google's Fix: Google is rolling out a fix for the issue,and users may need to update the Google Home app to the latest version. 2)Factory Reset: If you've already factory reset your device,you may need to temporarily set your phone's date back before March 9,2025, to allow the Chromecast to connect to Wi-Fi during the initial setup process.Once connected,the device will then update. Some questions are as follows: Q1)Is it second-generation Chromecast? Q2)What is the version Google Home app?Is it the latest version? Best Regards. Hank |
|
|
HI Hank This is a key update issue Let me explain the issue again. When tested, if the widevine key is incorrectly in the STB, the "Untrusted device" error is observed and the Chromecast does not work. > In Smart3 OS10, the correct sha256 value is observed by writing and reading the widevine key in the following way. (chromecast is OK ) BFX-AT100:/data # . ./wv_key.sh BFX-AT100:/data # echo $wv_key 4246582d41543130305f323031395f3030323439373638310000000000000000f8a1fe47048c10abdd2877ad544441c700000002000033ec69906caf79ecd7d7d51e5e9b87a974575a6cc7e5e21ad7f9b419ae97635f6287abea5a724a5cc5880a7c56fe772bea939316fa23bff3ca26e343480e1d732ef06b626f78af8f5beb BFX-AT100:/data # echo widevinekeybox > /sys/class/unifykeys/name BFX-AT100:/data # echo $wv_key | xxd -p -r > /sys/class/unifykeys/write BFX-AT100:/data # var=`busybox hexdump -e '16/1 "%02x"' /sys/class/unifykeys/read` BFX-AT100:/data # echo "$var" 7f3bd4d7566180ceebe84a7f55f6a33155cf7c9f49ca077d881d4fbb36174f65 > In Smart3 OS12, the incorrect sha256 value is observed by writing and reading the widevine key in the following way. (chromecast is Fail "Untrusted device") BFX-AT100:/data # . ./wv_key.sh BFX-AT100:/data # echo $wv_key 4246582d41543130305f323031395f3030323439373638310000000000000000f8a1fe47048c10abdd2877ad544441c700000002000033ec69906caf79ecd7d7d51e5e9b87a974575a6cc7e5e21ad7f9b419ae97635f6287abea5a724a5cc5880a7c56fe772bea939316fa23bff3ca26e343480e1d732ef06b626f78af8f5beb BFX-AT100:/data # echo widevinekeybox > /sys/class/unifykeys/name BFX-AT100:/data # echo $wv_key | xxd -p -r > /sys/class/unifykeys/write BFX-AT100:/data # var=`busybox hexdump -e '16/1 "%02x"' /sys/class/unifykeys/read` BFX-AT100:/data # echo "$var" f8d20e598df20877e4d826246fc31ffb4615cbc059aec9ec8e5b28951d844a3f > you can check the exact SHA256 value at the site below. https://emn178.github.io/online-tools/sha256.html I have also attached the image file. correct value is 7f3bd4d7566180ceebe84a7f55f6a33155cf7c9f49ca077d881d4fbb36174f65 And when I tested it, it's operating as follows. 1) Update widevine key on Smart3 OS10. chromecast is ok on Smart3 OS10 sha256 : 7f3bd4d7566180ceebe84a7f55f6a33155cf7c9f49ca077d881d4fbb36174f65 2) Update to Smart3 OS12 FW. chromecast is Fail sha256 : f8d20e598df20877e4d826246fc31ffb4615cbc059aec9ec8e5b28951d844a3f 3) Update to Smart3 OS10 again. chromecast is Fail sha256 : f8d20e598df20877e4d826246fc31ffb4615cbc059aec9ec8e5b28951d844a3f result : If it is updated to OS12, the key is being updated again, and the value is maintained. I don't understand the situation above. The key-write command FXN gave me as a guide is causing a problem with OS12. Please check it Thank you YK.Jung wv_key.sh (274 bytes) image-6.png (51,461 bytes) |
|
|
Hi Hank And I will also share the Smart3 FW. > Smart3 OS10 15.541.66 http://altserver01.duckdns.org/build_bot/BFX-AT100/OS10/15.541.66_BFX-AT100_5.4.1_VCS_2024-0229-150728.xml/ > Smart3 OS12 15.543.44 http://altserver01.duckdns.org/build_bot/BFX-AT100/OS12/15.543.44_BFX-AT100_5.4.3_2025-0107-150510.xml/ Thank you YK.Jung |
|
|
Hi Younkwang And when I tested it, it's operating as follows. 1) Update widevine key on Smart3 OS10. chromecast is ok on Smart3 OS10 sha256 : 7f3bd4d7566180ceebe84a7f55f6a33155cf7c9f49ca077d881d4fbb36174f65 2) Update to Smart3 OS12 FW. chromecast is Fail sha256 : f8d20e598df20877e4d826246fc31ffb4615cbc059aec9ec8e5b28951d844a3f 3) Update to Smart3 OS10 again. chromecast is Fail sha256 : f8d20e598df20877e4d826246fc31ffb4615cbc059aec9ec8e5b28951d844a3f >>Have you re-executed the key-write command after Step 3? As far as I know,the key-write command is used in OS10. Best Regards. Hank |
|
|
Hi Hank >>Have you re-executed the key-write command after Step 3? It is being written again normally. chromecast is ok on Smart3 OS10 sha256 : 7f3bd4d7566180ceebe84a7f55f6a33155cf7c9f49ca077d881d4fbb36174f65 >> As far as I know,the key-write command is used in OS10. After writing the key, we have to upgrade to OS12. The write key value in OS10 is changed in OS12. Please check it ASAP Thank you YK.Jung |
|
|
Hi Younkwang The key-write command is only used in OS10.So please don't use in OS12. Best Regards. Hank |
|
|
Hi Hank we write Key on OS10. However, if we update to OS12 FW, the key that was previously written will be changed. Please check it Thank you YK.Jung |
|
|
Hi Younkwang Can you provide the steps for the upgrade? It is normal to write Key on OS10 and update to OS12 via OTA. Best Regards. Hank |
|
|
Hi Hank You can check with the FXN engineer. And the upgrade document I have shares Please check it quickly. Thank you YK.Jung |
|
|
Hi Younkwang We don't have Chromecast device.Can you help capture the logcat? We need the debug logs from when the Chromecast connnects until it shows "Untrusted device" message. By the way, we will use factory firmware for retest.Please wait. Best Regards. Hank |
|
|
Hi Hank You can test it, too. https://support.google.com/chromecast/answer/2995235?hl=en 1) Prepare an Android phone. 2) STB and phones(wifi) are connected in the same network. 3) Run Youtube. 3) Click the cast icon above YouTube. If the widevine key is not normal on the STB, the "Untrusted device" window is displayed. If the widevine key is normal. youTube runs on STB Thank you YK.Jung |
|
|
Hi Hank I received the following usage command from FXN. =========================================================================== .. 2. For wvkey, get corresponding wv keys from keylist_SK168 file (e.g. 4246582...b47ec3b3) 2.2 echo widevinekeybox > /sys/class/unifykeys/name 2.3 echo $wv_key | xxd -p -r > /sys/class/unifykeys/write .. 5.Verify whether the written wvkey is correct 5.1 adb shell 5.2 echo widevinekeybox > /sys/class/unifykeys/name 5.3 var=`busybox hexdump -e '16/1 "%02x"' /sys/class/unifykeys/read` 5.4 echo "$var" 5.5 sha_src=`echo $wv_key | xxd -p -r | sha256sum | awk '{print $1}'` 5.6 echo "SRC WVKEY sha256sum=$sha_src" 5.7 Compare the output of echo "$var" with echo "SRC WVKEY sha256sum=$sha_src".If they are the same, it indicates that the wvkey has been set successfully =========================================================================== We need to make sure this is the right way. This step is works fine in OS10, but not in OS12. Please check it. Thank you YK.Jung |
|
|
Hi YK, status update: 1.we are replicating the process of the production line, covering things from the factory FW & key burning to customer FW burning, to verify the status of key changes. 2.the issue of widevine key changes after OTA to ATV12 has been sync to the AML TW FAE. AML TW FAE informed us that AML KR FAE is currently addressing this issue. If ALT has anything new, please inform us , and we will conduct local verification simultaneously Thank you |
|
|
Hi Willin Please proceed in the order below. 1) Apply the following two patches to OS10 and build. emmc-unifykey-backup.zip 2) Write the Key on the built 1)FW. 3) Upgrade to OS12 Verify that the written key is maintained in OS10. we haven't done enough testing yet. Please check it. Thank you YK.Jung |
|
|
Hi Willin Did you check test ? The key has been updated normally, but YouTube chromecast may not work. It is currently being checked. Please check about AOSP key update. And Please explain in detail how to write the key in FXN production line. we have to check whether it is the same as this method or not. Thank you YK.Jung |
|
|
Hi Willin The current progress update is as follows. First of all, I reported two issues to AML Kor. 1) When updating to OS12 after applying the emmc-unifykey-backup patch in OS10, the key value is maintained, but chromcast is not working. I have delivered issue log to AML Kor 2) When writing the following keys in OS12, sha256 is not writing normally. =========================================================================== .. 2. For wvkey, get corresponding wv keys from keylist_SK168 file (e.g. 4246582...b47ec3b3) 2.2 echo widevinekeybox > /sys/class/unifykeys/name 2.3 echo $wv_key | xxd -p -r > /sys/class/unifykeys/write .. =========================================================================== I have delivered issue log to AML Kor but I haven't received feedback from AML Kor yet. I'll update you if there's anything And when I tested it, there seems to be no problem with Key applied by FXN at the time of production. please let me know if there is anything that can be a clue. Thank you YK.Jung |
|
|
Hi YK, Status update: 1.the key change issue has been replicated: 1). burning the factory FW by usb buring tools, 2). write the device id & unify key, 3). OTA to OS12, 4) the device id unchanged, but unify key changed. 2.we are downloading the codes of OS 12 . we will pull the OS 10 code when OS12 download completed, and then apply the patches of "emmc-unifykey-backup", and proceed with keys burning. 3.the process for Keys burnin on the production line is roughly as follows: factory FW burnin --> write the MAC of Eth & BT --> write the Device ID , HDCP14 , Widevine Key , Playready Keys --> Network Function Test ... --> customer fw burin --> check & package. Thank you |
|
|
HI Willin >> 3.the process for Keys burnin on the production line is roughly as follows: factory FW burnin --> write the MAC of Eth & BT --> write the Device ID , HDCP14 , Widevine Key , Playready Keys --> <<----------------- Please further explain details on the commands and methods FXN use Network Function Test ... --> customer fw burin --> check & package. Thank you YK.Jung |
|
|
Hi Younkwang The details of writing keys are as follows: #Device ID echo deviceid > /sys/class/unifykeys/name echo $deviceid > /sys/class/unifykeys/write #HDCP14 echo hdcp > /sys/class/unifykeys/name echo $hdcp14 | xxd -p -r > /sys/class/unifykeys/write #Widevine Key echo widevinekeybox > /sys/class/unifykeys/name echo $wv_key | xxd -p -r > /sys/class/unifykeys/write #Playready Keys echo prprivkeybox > /sys/class/unifykeys/name dd if=$priv_key_path of=/sys/class/unifykeys/write echo "write playready private key $priv_key_path" > /dev/console echo prpubkeybox > /sys/class/unifykeys/name size=`stat -c "%s" $pub_key_path` busybox dd if=$pub_key_path of=/sys/class/unifykeys/write bs=$size count=1 echo "write playready public key $pub_key_path $size" > /dev/console Best Regards. Hank |
|
|
Hi Hank Thank you for update. - is this method UHD4 or Smart3? (There's no way to use writeAttentionkey ??) - Is there a difference between Smart3 and UHD4 in the type of keys that write during production? Because of this issue, SKB has a strong complaint against us. Please check it (ASAP) Thank you YK.Jung |
|
|
Hi Younkwang - is this method UHD4 or Smart3? (There's no way to use writeAttentionkey ??) >>Both are the same.The Attentionkey will be written after Playready Keys. - Is there a difference between Smart3 and UHD4 in the type of keys that write during production? >>The production line process of Smart3 and UHD4 are the same. Thank you Hank |
|
|
Hi Hank , Willin SKB is asking us to check the following. - What kind of symptoms can occur if the Widevine key is wrong? - What kind of symptoms can occur if the Attentionkey key is wrong? Please let me know after checking Thank you YK.Jung |
|
|
Hi Willin,Hank After applying the patch of 0017514, the key is ok(Sha256) in OS12, but Cast function is not working. So I asked Soc to check and received feedback as below now. ============================================================================================ The Google cast function must match exactly the device information registered on Google. Please first check if the device information upgraded to UHD4 --> Smart3 matches the information registered on Google. ============================================================================================ How should I check it ? , please let me know. Thank you YK.Jung |
|
|
Hi Willin,Hank As we did the test, we changed almost UHD4 STB to Smart3. There seems to be a difference in behavior when there is an existing UHD4 key And for the whole test and repeat test, the UHD4 initial key state must be restored So please share the 2 key pairs (deviceid , widevinekeybox,writeAttestaionkey) of real UHD4 keys for testing. Thank you YK.Jung |
|
|
Hi YK, we sent a case request to google to inquire about issues to the whitelist for key and "untrusted device" of cast services last week. google has responded to our email, requesting the DEVICE and KEYS information . please provide details about the devices and keys of generating error messages "untrusted device". Thank you. Screenshot from 2025-05-05 09-52-49.png (46,236 bytes) |
|
|
HI Willin I will update you on the progress so far I received the contents of the SoC to try the following command if there is a problem with OS12 BFX-AT100:/ # tee_provision -q -t 0x11 [PROVISION-CA] query [0x11 WIDEVINE_KEY] provisioned in RPMB, length = 128 bytes BFX-AT100:/ # tee_provision -d -t 0x11 When I used the above two commands, it was confirmed that BFX-AT100 worked properly at OS12 (we haven't tested it enough yet.) the old key(AOSP) is backed up into the RPMB area in widevine TA's logic at OS12 , ( but we don't know the exact timing, ) And this old key (AOSP key) seems to continue to be used in widebine. Therefore, when BFX-AT100 clears the key in RPMB area, it seems to work normally If there's anything you can check about this, please check it And we don't have the keys of BFX-UH200(AOSP). please share the two key pairs of BFX-UH200 for the repeat test, Thank you YK.Jung |
|
|
Hi YK, AOSP does not support Widevine keys , it's not possible to apply Widevine key from Google for AOSP devices. the Keys provided in Feb and Apr. are use for the AT100 (ATV) model. Thank you. |
|
|
HI Willin I updated the key from UHD4 to Smart3 once How do I return it to the UHD4 original state on this next test? All the UHD4 boxes that are already here have already been updated to smart3 key. That's why I'm asking for a keys for UHD4. If I put a Smart3 key in UHD4 and test it, the problem will not occur even if the key is not updated. QA team can't check it during the repeat test. So I am requesting an AOSP key to return to the original state of UHD4. Thank you YK.Jung |
|
|
Hi Willin Please give us your feedback about 0002028:0017526, which is SKB's confirmation request. Thank you YK.Jung |
|
|
- What kind of symptoms can occur if the Widevine key is wrong? === we use the exoplayer to check the key is available. if the key is wrong, the DRM sample will fail to play (black screen), the app will response with: "Playback error," "Unable to decrypt content," etc. the logcat error Messages: Widevine key invalid," "Decryption failed", etc. - What kind of symptoms can occur if the Attentionkey key is wrong? === we use the google script and app(AttestationTestTool) to check the att key is available. if the key is ok, the script will show msg: 'Finished. Failures: 0', if the key is someting wrong, the script will print the error message like 'AttestationFailInfo','AttestationFail'. or the key is empty, the message will show 'Attestation test did not complete, check logcat to determine the source of the error' Thank you |
|
|
Hi Willin There are additional things that need to be checked. SKB has UHD4 STBs collected from the user. Is it possible to convert UHD4 to Smart3 using the amlogic burning tool on UHD4 STBs? - it will be worked on it at ALT - only the key (deviceID/widevineKeybox/Attestation.keybox) required for Smart3 switching should be updated Please check if it is possible. Thank you YK.Jung |
|
|
Hi YK, The sop we provide is the workflow for the production line. Currently, we don't have UDH4 boards available here. Please use the local boards and burning tools for testing and evaluating the results. Thank you |
- yk.jung ( (ALTech) Younkwang Jung ) developer
.png)
.png)
.png)
